# Deploying Dagster on Heroku

Here you should include one short description about the Heroku, and why it's a good fit for Dagster

<div className="w-full h-48 bg-gray-50 flex items-center justify-center">
  Cover Image
</div>

## Description of X by itself

<TODO />

## Deployment Architecture

<!-- This diagram should show how the various dagster components are deployed on X. For example, in AWS:
    - The storages would be shown running on RDS
    - The dagster-daemon might be running in its own EC2 instance but networked to RDS
-->

<PlaceholderImage caption="Architecture Diagram" />

## Dagster components

- What Dagster components need to be deployed?

  - Dagit, Daemon, Database, Run Worker, User Code

- Map Dagster components (daemon, dagit, DB, workers) to X component or cloud products

## Deployment Walkthrough

### Step 1: Create a dagster project

If you do not already have Dagster installed, follow the instructions on the [Installation](/getting-started/install) page.

Once you have Dagster installed, run the `new-project` command to scaffold a new project.

    $ dagster new-project

### Step 2-X: TODO

- Step by step guide on how to deploy Dagster onto X to make sure everything runs as expected with default settings
- Components to deploy:

  - Dagit
  - Daemon
  - Storages (Database)
  - User Code
  - Heroku-specific compute log manager, if any
  - Heroku-specific IO Managers, if any

## Configuration

- How to further configure the Dagster instance

## \[Optional] CI/CD

- If the platform supports it, how to set up CI/CD in a way that works with Dagster

## Conclusion

- Summary
- Further learning materials, e.g. relevant Heroku docs

```
```
